Real-Time Data Acquisition and Recording System

ABSTRACT

A data acquisition and recording system (DARS) for mobile assets that includes a data recorder. The data recorder includes a data encoder, an onboard data manager, a vehicle event detector, at least one local memory component, and a queuing repository. DARS processes data from at least one input sensor and stores a compressed record of the data at least once per second in the local memory module. DARS is designed to run in near real-time mode, storing a full record comprising five minutes of data to a remote memory module every five minutes, and in real-time mode, streaming data to the remote memory module by uploading a record of data at least once per second and up to once every tenth of a second. Remotely located users can view video, audio, and data acquired by DARS through a web browser, which provides for quicker emergency response, validate the effectiveness of repairs and rerouting, and monitor crew performance and safety.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application claims priority to U.S. Provisional Application No.62/337,227, filed May 16, 2016, claims priority to U.S. ProvisionalApplication No. 62/337,225, filed May 16, 2016, claims priority to U.S.Provisional Application No. 62/337,228, filed May 16, 2016, and claimspriority to and is a continuation of U.S. Non-provisional applicationSer. No. 15/595,650, filed May 15, 2017, to the extent allowed by lawand the contents of which are incorporated herein by reference in theirentireties.

TECHNICAL FIELD

This disclosure relates to equipment used in high value assets andparticularly, to real-time data acquisition and recording systems usedin high value mobile assets.

BACKGROUND

High value mobile assets such as locomotives, aircraft, mass transitsystems, mining equipment, transportable medical equipment, cargo,marine vessels, and military vessels typically employ onboard dataacquisition and recording “black box” systems and/or “event recorder”systems. These data acquisition and recording systems, such as eventdata recorders or flight data recorders, log a variety of systemparameters used for incident investigation, crew performance evaluation,fuel efficiency analysis, maintenance planning, and predictivediagnostics. A typical data acquisition and recording system comprisesdigital and analog inputs, as well as pressure switches and pressuretransducers, which record data from various onboard sensor devices.Recorded data may include such parameters as speed, distance traveled,location, fuel level, engine revolution per minute (RPM), fluid levels,operator controls, pressures, current and forecasted weather conditionsand ambient conditions. In addition to the basic event and operationaldata, video and audio event/data recording capabilities are alsodeployed on many of these same mobile assets. Typically, data isextracted from data recorders, after an incident has occurred involvingan asset and investigation is required, once the data recorder has beenrecovered. Certain situations may arise where the data recorder cannotbe recovered or the data is otherwise unavailable. In these situations,the data, such as event and operational data, video data, and audiodata, acquired by the data acquisition and recording system is neededpromptly regardless of whether physical access to the data acquisitionand recording system or the data is available.

SUMMARY

This disclosure relates generally to real-time data acquisition andrecording systems used in high value mobile assets. The teachings hereincan provide real-time, or near real-time, access to data, such as eventand operational data, video data, and audio data, recorded by areal-time data acquisition and recording system on a high value mobileasset. One implementation of a method for processing, storing, andtransmitting data from a mobile asset described herein includesreceiving, using a data recorder onboard the mobile asset, data based onat least one data signal from at least one of: at least one data sourceonboard the mobile asset; and at least one data source remote from themobile asset; encoding, using a data encoder of the data recorder, arecord comprising a bit stream based on the data; appending, using anonboard data manager of the data recorder, the record to a record block;and storing, using the onboard data manager, the record block at aconfigurable first predetermined rate in at least one local memorycomponent of the data recorder and a queuing repository of the datarecorder.

Another implementation of a method for processing, storing, andtransmitting data from a mobile asset described herein includesreceiving data signals from at least one input sensor onboard the mobileasset; encoding a record comprising a bit stream based on the datasignals; appending the record to a record block comprising a pluralityof records; storing the record block to at least one local memorycomponent onboard the mobile asset; and storing the record block to aremote memory component on a condition that the plurality of recordscomprises a predetermined amount of data.

One implementation of a real-time data acquisition and recording systemdescribed herein includes a data recorder onboard the mobile assetcomprising at least one local memory component, a data encoder, anonboard data manager, and a queuing repository, the data recorderconfigured to receive data based on at least one data signal from atleast one of: at least one data source onboard the mobile asset; and atleast one data source remote from the mobile asset; the data encoderconfigured to encode a record comprising a bit stream based on the data;the onboard data manager configured to: append the record to a recordblock; and store the record block at a configurable first predeterminedrate in the at least one local memory component and the queuingrepository.

Another implementation of a system for processing, storing, andtransmitting data from a mobile asset described herein includes a dataencoder configured to receive data signals from at least one inputsensor onboard the mobile asset and compress the data signals into arecord comprising a bit stream; and an onboard data manager configuredto: append the record to a record block comprising a plurality ofrecords; store the record block in a crash hardened memory componentonboard the mobile asset; and store the record block to a remote memorycomponent on a condition that the plurality of records comprises apredetermined amount of data.

Variations in these and other aspects of the disclosure will bedescribed in additional detail hereafter.

BRIEF DESCRIPTION OF THE DRAWINGS

The description herein makes reference to the accompanying drawingswherein like reference numerals refer to like parts throughout theseveral views, and wherein:

FIG. 1 illustrates a field implementation of a first embodiment of anexemplary real-time data acquisition and recording system in accordancewith implementations of this disclosure;

FIG. 2 illustrates a field implementation of a second embodiment of theexemplary real-time data acquisition and recording system in accordancewith implementations of this disclosure;

FIG. 3 is a flow diagram of a process for recording data and/orinformation from a mobile asset in accordance with implementations ofthis disclosure;

FIG. 4 is a flow diagram of a process for appending data and/orinformation from the mobile asset after a power outage in accordancewith implementations of this disclosure;

FIG. 5 is a diagram that illustrates exemplary interim record blocks andfull record blocks saved to a crash hardened memory module in accordancewith implementations of this disclosure;

FIG. 6 is a diagram that illustrates exemplary interim record blocks inthe crash hardened memory module prior to a power outage and afterrestoration of power in accordance with implementations of thisdisclosure; and

FIG. 7 is a diagram that illustrates an exemplary record segment in thecrash hardened memory module after power has been restored in accordancewith implementations of this disclosure.

DETAILED DESCRIPTION

A real-time data acquisition and recording system described hereinprovides real-time, or near real-time, access to a wide range of data,such as event and operational data, video data, and audio data, relatedto a high value asset to remotely located users such as asset owners,operators and investigators. The data acquisition and recording systemrecords data, via a data recorder, relating to the asset and streams thedata to a remote data repository and remotely located users prior to,during, and after an incident has occurred. The data is streamed to theremote data repository in real-time, or near real-time, makinginformation available at least up to the time of an incident oremergency situation, thereby virtually eliminating the need to locateand download the “black box” in order to investigate an incidentinvolving the asset and eliminating the need to interact with the datarecorder on the asset to request a download of specific data, to locateand transfer files, and to use a custom application to view the data.The system of the present disclosure retains typical recordingcapability and adds the ability to stream data to a remote datarepository and remote end user prior to, during, and after an incident.In the vast majority of situations, the information recorded in the datarecorder is redundant and not required as data has already been acquiredand stored in the remote data repository.

Prior to the system of the present disclosure, data was extracted fromthe “black box” or “event recorder” after an incident had occurred andan investigation was required. Data files containing time segmentsrecorded by the “black box” had to be downloaded and retrieved from the“black box” and then viewed by a user with proprietary software. Theuser would have to obtain physical or remote access to the asset, selectthe desired data to be downloaded from the “black box,” download thefile containing the desired information to a computing device, andlocate the appropriate file with the desired data using a customapplication that operates on the computing device. The system of thepresent disclosure has eliminated the need for the user to perform thesesteps, only requiring the user to use a common web browser to navigateto the desired data.

A remotely located user, such as an asset owner, operator, and/orinvestigator, may access a common web browser to navigate to live and/orhistoric desired data relating to a selected asset to view and analyzethe operational efficiency and safety of assets in real-time or nearreal-time. The ability to view operations in real-time, or nearreal-time, enables rapid evaluation and adjustment of behavior. Duringan incident, for example, real-time information and/or data canfacilitate triaging the situation and provide valuable information tofirst responders. During normal operation, for example, real-timeinformation and/or data can be used to audit crew performance and to aidnetwork wide situational awareness.

Data may include, but is not limited to, analog and frequency parameterssuch as speed, pressure, temperature, current, voltage, and accelerationwhich originate from the asset and/or nearby assets, Boolean data suchas switch positions, actuator position, warning light illumination, andactuator commands, global positioning system (GPS) data and/orgeographic information system (GIS) data such as position, speed, andaltitude, internally generated information such as the regulatory speedlimit for an asset given its current position, video and imageinformation from cameras located at various locations in, on or in thevicinity of the asset, audio information from microphones located atvarious locations in, on or in vicinity of the asset, information aboutthe operational plan for the asset that is sent to the asset from a datacenter such as route, schedule, and cargo manifest information,information about the environmental conditions, including current andforecasted weather conditions, of the area in which the asset iscurrently operating in or is planned to operate in, asset control statusand operational data generated by systems such as positive train control(PTC) in locomotives, and data derived from a combination from any ofthe above including, but not limited to, additional data, video, andaudio analysis and analytics.

FIGS. 1 and 2 illustrate a field implementation of a first embodimentand a second embodiment, respectively, of an exemplary real-time dataacquisition and recording system (DARS) 100, 200 in which aspects of thedisclosure can be implemented. DARS 100, 200 is a system that deliversreal time information to remotely located end users from a datarecording device. DARS 100, 200 includes a data recorder 154, 254 thatis installed on a vehicle or mobile asset 148, 248 and communicates withany number of various information sources through any combination ofonboard wired and/or wireless data links 170, 270, such as a wirelessgateway/router, or off board information sources via a data center 150,250 of DARS 100, 200 via data links such as wireless data links 146.Data recorder 154, 254 comprises an onboard data manager 120, 220, adata encoder 122, 222, a vehicle event detector 156, 256, a queuingrepository 158, 258, and a wireless gateway/router 172, 272.Additionally, in this implementation, data recorder 154, 254 can includea crash hardened memory module 118, 218 and/or an Ethernet switch 162,262 with or without power over Ethernet (POE). An exemplary hardenedmemory module 118, 218 can be, for example, a crashworthy event recordermemory module that complies with the Code of Federal Regulations and theFederal Railroad Administration regulations, a crash survivable memoryunit that complies with the Code of Federal Regulations and the FederalAviation Administration regulations, a crash hardened memory module incompliance with any applicable Code of Federal Regulations, or any othersuitable hardened memory device as is known in the art. In the secondembodiment, shown in FIG. 2, the data recorder 254 can further includean optional non-crash hardened removable storage device 219.

The wired and/or wireless data links 170, 270 can include any one of orcombination of discrete signal inputs, standard or proprietary Ethernet,serial connections, and wireless connections. Ethernet connected devicesmay utilize the data recorder's 154, 254 Ethernet switch 162, 262 andcan utilize POE. Ethernet switch 162, 262 may be internal or externaland may support POE. Additionally, data from remote data sources, suchas a map component 164, 264, a route/crew manifest component 124, 224,and a weather component 126, 226 in the implementation of FIGS. 1 and 2,is available to the onboard data manager 120, 220 and the vehicle eventdetector 156, 256 from the data center 150, 250 through the wirelessdata link 146, 246 and the wireless gateway/router 172, 272.

Data recorder 154, 254 gathers data or information from a wide varietyof sources, which can vary widely based on the asset's configuration,through onboard data links 170, 270. The data encoder 122, 222 encodesat least a minimum set of data that is typically defined by a regulatoryagency. In this implementation, the data encoder 122, 222 receives datafrom a wide variety of asset 148, 248 sources and data center 150, 250sources. Information sources can include any number of components in theasset 148, 248, such as any of analog inputs 102, 202, digital inputs104, 204, I/O module 106, 206, vehicle controller 108, 208, enginecontroller 110, 210, inertial sensors 112, 212, global positioningsystem (GPS) 114, 214, cameras 116, 216, positive train control(PTC)/signal data 166, 266, fuel data 168, 268, cellular transmissiondetectors (not shown), internally driven data and any additional datasignals, and any of number of components in the data center 150, 250,such as any of the route/crew manifest component 124, 224, the weathercomponent 126, 226, the map component 164, 264, and any additional datasignals. The data encoder 122, 222 compresses or encodes the data andtime synchronizes the data in order to facilitate efficient real-timetransmission and replication to a remote data repository 130, 230. Thedata encoder 122, 222 transmits the encoded data to the onboard datamanager 120, 220 which then saves the encoded data in the crash hardenedmemory module 118, 218 and the queuing repository 158, 258 forreplication to the remote data repository 130, 230 via a remote datamanager 132, 232 located in the data center 150, 250. Optionally, theonboard data manager 120, 220 can save a tertiary copy of the encodeddata in the non-crash hardened removable storage device 219 of thesecond embodiment shown in FIG. 2. The onboard data manager 120, 220 andthe remote data manager 132, 232 work in unison to manage the datareplication process. A single remote data manager 132, 232 in the datacenter 150, 250 can manage the replication of data from a plurality ofassets 148, 248.

The data from the various input components and data from an in-cabaudio/graphic user interface (GUI) 160, 260 are sent to a vehicle eventdetector 156, 256. The vehicle event detector 156, 256 processes thedata to determine whether an event, incident or other predefinedsituation involving the asset 148, 248 has occurred. When the vehicleevent detector 156, 256 detects signals that indicate a predefined eventoccurred, the vehicle event detector 156, 256 sends the processed datathat a predefined event occurred along with supporting data surroundingthe predefined event to the onboard data manager 120, 220. The vehicleevent detector 156, 256 detects events based on data from a wide varietyof sources, such as the analog inputs 102, 202, the digital inputs 104,204, the I/O module 106, 206, the vehicle controller 108, 208, theengine controller 110, 210, the inertial sensors 112, 212, the GPS 114,214, the cameras 116, 216, the route/crew manifest component 124, 224,the weather component 126, 226, the map component 164, 264, thePTC/signal data 166, 266, and the fuel data 168, 268, which can varybased on the asset's configuration. When the vehicle event detector 156,256 detects an event, the detected asset event information is stored ina queuing repository 158, 258 and can optionally be presented to thecrew of the asset 148, 248 via the in-cab audio/graphical user interface(GUI) 160, 260.

The onboard data manager 120, 220 also sends data to the queuingrepository 158. In near real-time mode, the onboard data manager 120,220 stores the encoded data received from the data encoder 122, 222 andany event information in the crash hardened memory module 118, 218 andin the queuing repository 158, 258. In the second embodiment of FIG. 2,the onboard data manager 220 can optionally store the encoded data inthe non-crash hardened removable storage device 219. After five minutesof encoded data has accumulated in the queuing repository 158, 258, theonboard data manager 120, 220 stores the five minutes of encoded data tothe remote data repository 130, 230 via the remote data manager 132, 232in the data center 150, 250 over the wireless data link 146, 256accessed through the wireless gateway/router 172, 272. In real-timemode, the onboard data manager 120, 220 stores the encoded data receivedfrom the data encoder 122, 222 and any event information to the crashhardened memory module 118, 218, and optionally in the non-crashhardened removable storage device 219 of FIG. 2, and to the remote datarepository 130, 230 via the remote data manager 132, 232 in the datacenter 150, 250 over the wireless data link 146, 246 accessed throughthe wireless gateway/router 172, 272. The onboard data manager 120, 220and the remote data manager 132, 232 can communicate over a variety ofwireless communications links, such as Wi-Fi, cellular, satellite, andprivate wireless systems utilizing the wireless gateway/router 172, 272.Wireless data link 146, 246 can be, for example, a wireless local areanetwork (WLAN), wireless metropolitan area network (WMAN), wireless widearea network (WWAN), a private wireless system, a cellular telephonenetwork or any other means of transferring data from the data recorder154, 254 of DARS 100, 200 to, in this example, the remote data manager130, 230 of DARS 100, 200. When a wireless data connection is notavailable, the data is stored in memory and queued in queuing repository158, 258 until wireless connectivity is restored and the datareplication process can resume.

In parallel with data recording, data recorder 154, 254 continuously andautonomously replicates data to the remote data repository 130, 230. Thereplication process has two modes, a real-time mode and a near real-timemode. In real-time mode, the data is replicated to the remote datarepository 130, 230 every second. In near real-time mode, the data isreplicated to the remote data repository 130, 230 every five minutes.The rate used for near real-time mode is configurable and the rate usedfor real-time mode can be adjusted to support high resolution data byreplicating data to the remote data repository 130, 230 every 0.10seconds. When the DARS 100, 200 is in near real-time mode, the onboarddata manager 120, 220 queues data in the queuing repository 158, 258before replicating the data to the remote data manager 132, 232. Theonboard data manager 120, 220 also replicates the vehicle event detectorinformation queued in the queuing repository 158, 258 to the remote datamanager 132, 232. Near real-time mode is used during normal operation,under most conditions, in order to improve the efficiency of the datareplication process.

Real-time mode can be initiated based on events occurring and detectedby the vehicle event detector 156, 256 onboard the asset 148, 248 or bya request initiated from the data center 150, 250. A typical data center150, 250 initiated request for real-time mode is initiated when aremotely located user 152, 252 has requested real-time information froma web client 142, 242. A typical reason for real-time mode to originateonboard the asset 148, 248 is the detection of an event or incident bythe vehicle event detector 156, 256 such as an operator initiating anemergency stop request, emergency braking activity, rapid accelerationor deceleration in any axis, or loss of input power to the data recorder154, 254. When transitioning from near real-time mode to real-time mode,all data not yet replicated to the remote data repository 130, 230 isreplicated and stored in the remote data repository 130, 230 and thenlive replication is initiated. The transition between near real-timemode and real-time mode typically occurs in less than five seconds.After a predetermined amount of time has passed since the event orincident, a predetermined amount of time of inactivity, or when the user152, 252 no longer desires real-time information from the asset 148,248, the data recorder 154, 254 reverts to near real-time mode. Thepredetermined amount of time required to initiate the transition isconfigurable and is typically set to ten minutes.

When the data recorder 154, 254 is in real-time mode, the onboard datamanager 120, 220 attempts to continuously empty its queue to the remotedata manager 132, 232, storing the data to the crash hardened memorymodule 118, 218, and optionally to the non-crash hardened removablestorage device 219 of FIG. 2, and sending the data to the remote datamanager 132, 232 simultaneously. The onboard data manager 120, 220 alsosends the detected vehicle information queued in the queuing repository158, 258 to the remote data manager 132, 232.

Upon receiving data to be replicated from the data recorder 154, 254,along with data from the map component 164, 264, the route/crew manifestcomponent 124, 224, and the weather component 126, 226, the remote datamanager 132, 232 stores the compressed data to the remote datarepository 130, 230 in the data center 150, 250 of DARS 100, 200. Theremote data repository 130, 230 can be, for example, cloud-based datastorage or any other suitable remote data storage. When data isreceived, a process is initiated that causes a data decoder 136, 236 todecode the recently replicated data for/from the remote data repository130, 230 and send the decoded data to a remote event detector 134, 234.The remote data manager 132, 232 stores vehicle event information in theremote data repository 130, 230. When the remote event detector 134, 234receives the decoded data, it processes the decoded data to determine ifan event of interest is found in the decoded data. The decodedinformation is then used by the remote event detector 134, 234 to detectevents, incidents, or other predefined situations, in the data occurringwith the asset 148, 248. Upon detecting an event of interest from thedecoded data, the remote event detector 134, 234 stores the eventinformation and supporting data in the remote data repository 130, 230.When the remote data manager 132, 232 receives remote event detector134, 234 information, the remote data manager 132, 232 stores theinformation in the remote data repository 130, 230.

The remotely located user 152, 252 can access information, includingvehicle event detector information, relating to the specific asset 148,248, or a plurality of assets, using the standard web client 142, 242,such as a web browser, or a virtual reality device (not shown) which, inthis implementation, can display thumbnail images from selected cameras.The web client 142, 242 communicates the user's 152, 252 request forinformation to a web server 140, 240 through a network 144, 244 usingcommon web standards, protocols, and techniques. Network 144, 244 canbe, for example, the Internet. Network 144, 244 can also be a local areanetwork (LAN), metropolitan area network (MAN), wide area network (WAN),virtual private network (VPN), a cellular telephone network or any othermeans of transferring data from the web server 140, 240 to, in thisexample, the web client 142, 242. The web server 140, 240 requests thedesired data from the data decoder 136, 236. The data decoder 136, 236obtains the requested data relating to the specific asset 148, 248, or aplurality of assets, from the remote data repository 130, 230 uponrequest from the web server 140, 240. The data decoder 136, 236 decodesthe requested data and sends the decoded data to a localizer 138, 238.Localization is the process of converting data to formats desired by theend user, such as converting the data to the user's preferred languageand units of measure. The localizer 138, 238 identifies the profilesettings set by user 152, 252 by accessing the web client 142, 242 anduses the profile settings to prepare the information being sent to theweb client 142, 242 for presentation to the user 152, 252, as the rawencoded data and detected event information is saved to the remote datarepository 130, 230 using coordinated universal time (UTC) andinternational system of units (SI units). The localizer 138, 238converts the decoded data into a format desired by the user 152, 252,such as the user's 152, 252 preferred language and units of measure. Thelocalizer 138, 238 sends the localized data in the user's 152, 252preferred format to the web server 140, 240 as requested. The web server140, 240 then sends the localized data of the asset, or plurality ofassets, to the web client 142, 242 for viewing and analysis, providingplayback and real-time display of standard video and 360 degree video.The web client 142, 242 can display and the user 152, 252 can view thedata, video, and audio for a single asset or simultaneously view thedata, video, and audio for a plurality of assets. The web client 142,242 can also provide synchronous playback and real-time display of dataalong with the plurality of video and audio data from both standard and360 degree video sources on, in, or in the vicinity of the asset, nearbyassets, and/or remotely located sites.

FIG. 3 is a flow diagram showing a process 300 for recording data and/orinformation from the asset 148, 248 in accordance with an implementationof this disclosure. Data recorder 154, 254 receives data signals fromvarious input components that include physical or calculated dataelements from the asset 148, 248 and data center 150, 250, such asspeed, latitude coordinates, longitude coordinates, horn detection,throttle position, weather data, map data, or crew data 302. Dataencoder 122, 222 creates a record that includes a structured series ofbits used to configure and record the data signal information 304. Theencoded record is then sent to the onboard data manager 120, 220 thatsequentially combines a series of records in chronological order intorecord blocks that include up to five minutes of data 306. An interimrecord block includes less than five minutes of data while a full recordblock includes a full five minutes of data. Each record block includesall the data required to fully decode the included signals, including adata integrity check. At a minimum, a record block must start with astart record and end with an end record.

In order to ensure that all of the encoded signal data is saved to thecrash hardened memory module 118, and optionally to the non-crashhardened removable storage device 219 of FIG. 2, should the datarecorder 154, 254 lose power or be subjected to extreme temperatures ormechanical stresses due to a collision or other catastrophic event, theonboard data manager 120, 220 stores interim record blocks in the crashhardened memory module 118 at a predetermined rate 308, and optionallyin the non-crash hardened removable storage device 219 of FIG. 2, wherethe predetermined rate is configurable and/or variable, as shown in FIG.5 in an exemplary representation. Interim record blocks are saved atleast once per second but can also be saved as frequently as once everytenth of a second. The rate at which interim record blocks are saveddepends on the sampling rates of each signal. Every interim record blockincludes the full set of records since the last full record block. Datarecorder 154, 254 can alternate between two temporary storage locationsin the crash hardened memory module 118, 218, and optionally in thenon-crash hardened removable storage device 219 of FIG. 2, whenrecording each interim record block to prevent the corruption or loss ofmore than one second of data when the data recorder 154, 254 loses powerwhile storing data to the crash hardened memory module 118, 218 or theoptional non-crash hardened removable storage device 219 of the datarecorder 254 of FIG. 2. Each time a new interim record block is saved toa temporary crash hardened memory location it will overwrite theexisting previously stored interim record block in that location.

Every five minutes, in this implementation, when the data recorder 154,254 is in near real-time mode, the onboard data manager 120, 220 storesa full record block including the last five minutes of encoded signaldata into a record segment in the crash hardened memory module 118, 218,shown in FIG. 7, and sends a copy of the full record block to the remotedata manager 132, 232 to be stored in the remote data repository 130,230 for a predetermined retention period such as two years 310. Thecrash hardened memory module 118, 218, and/or the optional non-crashhardened removable storage device 219 of the data recorder 254 of FIG.2, stores a record segment of the most recent record blocks for amandated storage duration, which in this implementation is the federallymandated duration that the data recorder 154, 254 must store operationalor video data in the crash hardened memory module 118, 218 with anadditional 24 hour buffer, and is then overwritten.

FIG. 4 is a flow diagram showing a process 400 for appending data and/orinformation from the asset 148, 248 after a power outage in accordancewith an implementation of this disclosure. Once power is restored, thedata recorder 154, 254 identifies the last interim record block that wasstored in one of the two temporary crash hardened memory locations 402and validates the last interim record block using the 32 bit cyclicredundancy check that is included in the end record of every recordblock 404. The validated interim record block is then appended to thecrash hardened memory record segment and that record segment, which cancontain up to five minutes of data prior to the power loss, is sent tothe remote data manager 132, 232 to be stored for the retention period406. The encoded signal data is stored to the crash hardened memorymodule 118, 218, and/or the optional non-crash hardened removablestorage device 219 of the data recorder 254 of FIG. 2, in a circularbuffer of the mandated storage duration. Since the crash hardened memoryrecord segment is broken up into multiple record blocks, the datarecorder 154, 254 removes older record blocks when necessary to free upmemory space each time a full record block is saved to crash hardenedmemory module 118, 218, and/or the optional non-crash hardened removablestorage device 219 of the data recorder 254 of FIG. 2.

FIG. 6 is a diagram that illustrates exemplary interim record blocksprior to a loss of power and after restoration of power to the datarecorder 154, 254. When the interim record block stored in temporarylocation 2 at (2/1/2016 10:10:08 AM) 602 is valid, that interim recordblock is appended to the record segment 702 (FIG. 7) in the crashhardened memory module 118, 218, and/or the optional non-crash hardenedremovable storage device 219 of the data recorder 254 of FIG. 2, asshown in FIG. 7. When the interim record block stored in temporarylocation 2 at (2/1/2016 10:10:08 AM) is not valid, the interim recordblock in temporary location 1 at (2/1/2016 10:10:07 AM) is validatedand, if valid, is appended to the record segment in the crash hardenedmemory module 118, 218, and/or the optional non-crash hardened removablestorage device 219 of the data recorder 254 of FIG. 2.

Whenever any record block needs to be saved in crash hardened memorymodule 118, 218, and/or the optional non-crash hardened removablestorage device 219 of the data recorder 254 of FIG. 2, the recordsegment is flushed to the disk immediately. Since the data recorder 154,254 alternates between two different temporary storage locations whensaving interim record blocks, there is always one temporary storagelocation that is not being modified or flushed to crash hardened memoryor non-crash hardened removable storage device, thereby ensuring that atleast one of the two interim record blocks stored in the temporarystorage locations is valid and that the data recorder 154, 254 will notlose more than one second at most of data whenever the data recorder154, 254 loses power. Similarly, when the data recorder 154, 254 iswriting data to the crash hardened memory module 118, 218, and/or theoptional non-crash hardened removable storage device 219 of the datarecorder 254 of FIG. 2, every tenth of a second, the data recorder 154,254 will not lose more than one tenth of a second at most of datawhenever the data recorder 154, 254 loses power.

For simplicity of explanation, process 300 and process 400 are depictedand described as a series of steps. However, steps in accordance withthis disclosure can occur in various orders and/or concurrently.Additionally, steps in accordance with this disclosure may occur withother steps not presented and described herein. Furthermore, not allillustrated steps may be required to implement a method in accordancewith the disclosed subject matter.

As used in this application, the term “or” is intended to mean aninclusive “or” rather than an exclusive “or”. That is, unless specifiedotherwise, or clear from context, “X includes A or B” is intended tomean any of the natural inclusive permutations. That is, if X includesA; X includes B; or X includes both A and B, then “X includes A or B” issatisfied under any of the foregoing instances. In addition, “X includesat least one of A and B” is intended to mean any of the naturalinclusive permutations. That is, if X includes A; X includes B; or Xincludes both A and B, then “X includes at least one of A and B” issatisfied under any of the foregoing instances. The articles “a” and“an” as used in this application and the appended claims shouldgenerally be construed to mean “one or more” unless specified otherwiseor clear from context to be directed to a singular form. Moreover, useof the term “an implementation” or “one implementation” throughout isnot intended to mean the same embodiment, aspect or implementationunless described as such.

While the present disclosure has been described in connection withcertain embodiments, it is to be understood that the disclosure is notto be limited to the disclosed embodiments but, on the contrary, isintended to cover various modifications and equivalent arrangementsincluded within the scope of the appended claims, which scope is to beaccorded the broadest interpretation so as to encompass all suchmodifications and equivalent structures as is permitted under the law.

What is claimed:
 1. A method for processing, storing, and transmittingdata from a mobile asset comprising: receiving, using a data recorderonboard the mobile asset, data based on at least one data signal from atleast one of: at least one data source onboard the mobile asset; and atleast one data source remote from the mobile asset; and encoding, usinga data encoder of the data recorder, encoded data based on apredetermined amount of the data.
 2. The method of claim 1, furthercomprising: storing, using the onboard data manager, the encoded data ata configurable first predetermined rate in at least one local memorycomponent of the data recorder and a queuing repository of the datarecorder.
 3. The method of claim 1, wherein at least one of: the atleast one data source onboard the mobile asset includes at least one ofanalog inputs, digital inputs, input and output modules, vehiclecontroller, engine controller, inertial sensors, global positioningsystem, at least one camera, fuel data, and positive train control (PTC)signal data, and wherein the at least one data source remote from themobile asset includes at least one of map components, route and crewmanifest component, and weather component; and the data includes atleast one of speed, pressure, temperature, current, voltage,acceleration from the mobile asset, acceleration from remote mobileassets, switch positions, actuator positions, warning lightillumination, actuator commands, position, altitude, internallygenerated information, video information, audio information, route,schedule, cargo manifest information, environmental conditions, currentweather conditions, and forecasted weather conditions.
 4. The method ofclaim 1, further comprising: identifying, using a vehicle event detectorof the data recorder, a predefined event based on at least one of thedata and multimedia data from at least one of an in cab audio and agraphical user interface (GUI) onboard the mobile asset on a conditionthat the predefined event occurred involving the mobile asset; storing,using the vehicle event detector, the predefined event, data, andmultimedia data in the queuing repository on the condition that thepredefined event occurred involving the mobile asset; and sending, usingthe vehicle event recorder, the predefined event, data, and multimediadata to the onboard data manager on the condition that the predefinedevent occurred involving the mobile asset.
 5. The method of claim 4,wherein the predefined event is at least one of an operator of themobile asset initiating an emergency stop request, emergency brakingactivity, rapid acceleration of the asset in any axis, rapiddeceleration of the asset in any axis, and loss of input power to thedata recorder.
 6. The method of claim 4, further comprising: displaying,using at least one of the in cab audio and the GUI onboard the mobileasset, at least one of the predefined event, data, and multimedia data.7. The method of claim 2, wherein the at least one local memorycomponent comprises at least one of a crash hardened memory module and anon-crash hardened removable storage device.
 8. The method of claim 2,wherein the encoded data is stored in one of at least 2 temporarystorage locations of the at least one local memory component.
 9. Themethod of claim 2, wherein storing the encoded data to the at least onelocal memory component comprises one of: storing the encoded data in afirst temporary storage location of the at least one local memorycomponent on a condition that a previous encoded data was stored in asecond temporary storage location of the at least one local memorycomponent; and storing the encoded data in the second temporary storagelocation of the at least one local memory component on a condition thatthe previous encoded data was stored in the first temporary storagelocation of the at least one local memory component.
 10. The method ofclaim 1, wherein the data recorder receives the data from at least oneof: the at least one data source onboard the mobile asset via at leastone of a wireless data link and a wired data link onboard the mobileasset; and the at least one data source remote from the mobile asset viathe wireless data link.
 11. The method of claim 10, further comprisingat least one of: receiving, using at least one of an Ethernet switch andpower of Ethernet of the data recorder, the data from the at least oneof the wireless data link and the wired data link; receiving, using atleast one of a wireless gateway and a wireless router of the datarecorder, the data from the wireless data link.
 12. The method of claim1, further comprises: time synchronizing, using the data encoder, theencoded data.
 13. The method of claim 2, further comprising: sending,using the onboard data manager, the encoded data to a remote datamanager via a wireless data link at a configurable second predeterminedrate, wherein the second predetermined rate is in the range of andincluding zero and one second; and storing, using the remote datamanager, the encoded data to a remote data repository.
 14. The method ofclaim 13, further comprising: decoding, using the data decoder, theencoded data into decoded data; identifying, using a remote eventdetector, a predefined event based on the decoded data on a conditionthat the predefined event occurred involving the mobile asset; andstoring, using the remote event detector, the predefined event anddecoded data in the remote data repository on the condition that thepredefined event occurred involving the mobile asset.
 15. The method ofclaim 2, further comprising: appending encoded data to a data segment;storing, using the onboard data manager, the data segment to the atleast one local memory component on a condition that the data segmentincludes a predetermined amount of encoded data.
 16. The method of claim15, further comprising: sending, using the onboard data manager, thedata segment to a remote data manager via a wireless data link at aconfigurable second predetermined rate.
 17. The method of claim 16,wherein the second predetermined rate is in the range of and includingzero to five minutes.
 18. The method of claim 16, further comprising:storing, using the remote data manager, the data segment in a remotedata repository.
 19. The method of claim 16, wherein the data segment issent to the remote data manager via the wireless data link at theconfigurable second predetermined rate, wherein the second predeterminedrate is in one of a first range of and including zero to one second on acondition that the data recorder is in real-time mode and a second rangeof and including zero to five minutes on a condition that the datarecorder is in near real-time mode.
 20. A system for processing,storing, and transmitting data from a mobile asset comprising: a datarecorder onboard the mobile asset comprising at least one local memorycomponent, a data encoder, an onboard data manager, and a queuingrepository, the data recorder adapted to receive data based on at leastone data signal from at least one of: at least one data source onboardthe mobile asset; and at least one data source remote from the mobileasset; and the data encoder adapted to encode encoded data based on thedata.
 21. The system of claim 20, further comprising: the onboard datamanager adapted to: store the encoded data at a configurable firstpredetermined rate in the at least one local memory component and thequeuing repository.
 22. The system of claim 20, wherein at least one of:the at least one data source onboard the mobile asset includes at leastone of analog inputs, digital inputs, input and output modules, vehiclecontroller, engine controller, inertial sensors, global positioningsystem, at least one camera, fuel data, and positive train control (PTC)signal data, and wherein the at least one data source remote from themobile asset includes at least one of map components, route and crewmanifest component, and weather component; and the data includes atleast one of speed, pressure, temperature, current, voltage,acceleration from the mobile asset, acceleration from remote mobileassets, switch positions, actuator positions, warning lightillumination, actuator commands, position, altitude, internallygenerated information, video information, audio information, route,schedule, cargo manifest information, environmental conditions, currentweather conditions, and forecasted weather conditions.
 23. The system ofclaim 20, further comprising: a vehicle event detector of the dataencoder, the vehicle event detector adapted to: identify a predefinedevent based on at least one of the data and multimedia data from an incab audio and graphical user interface (GUI) onboard the mobile asset ona condition that the predefined event occurred involving the mobileasset; store the predefined event, data, and multimedia data in thequeuing repository on the condition that the predefined event occurredinvolving the mobile asset; and send the predefined event, data, andmultimedia data to the onboard data manager on the condition that thepredefined event occurred involving the mobile asset.
 24. The system ofclaim 23, wherein the predefined event is at least one of an operator ofthe mobile asset initiating an emergency stop request, emergency brakingactivity, rapid acceleration of the asset in any axis, rapiddeceleration of the asset in any axis, or loss of input power to thedata recorder.
 25. The system of claim 23, wherein the in cab audio andGUI onboard the mobile asset displays at least one of the predefinedevent, data, and multimedia data.
 26. The system of claim 21, whereinthe at least one local memory component comprises at least one of acrash hardened memory module and a non-crash hardened removable storagedevice.
 27. The system of claim 21, wherein the encoded data is storedin one of at least 2 temporary storage locations of the at least onelocal memory component.
 28. The system of claim 21, wherein the onboarddata manager is adapted to: store the encoded data in a first temporarystorage location of the at least one local memory component on acondition that a previous encoded data was stored in a second temporarystorage location of the at least one local memory component; and storethe encoded data in the second temporary storage location of the atleast one local memory component on a condition that the previousencoded data was stored in the first temporary storage location of theat least one local memory component.
 29. The system of claim 20, furthercomprising: at least one of a wireless data link and a wired data linkonboard the mobile asset, wherein the at least one of the wireless datalink and the wired data link is adapted to receive the data from the atleast one data source onboard the mobile asset.
 30. The system of claim29, further comprising: at least one of an Ethernet switch and power ofEthernet of the data recorder, the at least one of the Ethernet switchand power over Ethernet adapted to receive the data from the at leastone of the wireless data link and the wired data link.
 31. The system ofclaim 20, further comprising at least one of: at least one wireless datalink adapted to receive the data from the at least one data sourceremote from the mobile asset; and at least one of a wireless gateway anda wireless router of the data recorder, the at least one of the wirelessgateway and the wireless router adapted to receive the data from thewireless data link.
 32. The system of claim 20, wherein the data encoderis adapted to time synchronize the data in the record.
 33. The system ofclaim 21, wherein the onboard data manager is adapted to: send apredetermined amount of the encoded data to a remote data manager via awireless data link at a configurable second predetermined rate, whereinthe second predetermined rate is in the range of and including zero andone second; and store the predetermined amount of the encoded data to aremote data repository.
 34. The system of claim 33, further comprising:a remote data decoder adapted to decode the predetermined amount ofencoded data into decoded data; and a remote event detector adapted to:identify a predefined event based on the decoded data on a conditionthat the predefined event occurred involving the mobile asset; and storethe predefined event and decoded data in the remote data repository onthe condition that the predefined event occurred involving the mobileasset.
 35. The system of claim 21, wherein the onboard data manager isadapted to: append the encoded data to a data segment; store the datasegment to the at least one local memory component on a condition that apredetermined amount of the encoded data comprises at least 0.10 secondsof encoded data.
 36. The system of claim 35, wherein the onboard datamanager is adapted to: send the data segment to a remote data managervia a wireless data link at a configurable second predetermined rate.37. The system of claim 36, wherein the second predetermined rate is inthe range of and including zero to five minutes.
 38. The system of claim36, wherein the remote data manager is adapted to store the data segmentin a remote data repository.
 39. The system of claim 36, wherein thedata segment is sent to the remote data manager via the wireless datalink at the configurable second predetermined rate, wherein the secondpredetermined rate is in one of a first range of and including zero toone second on a condition that the data recorder is in real-time modeand a second range of and including zero to five minutes on a conditionthat the data recorder is in near real-time mode.